Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
It looks like wine is installed in /usr/local/... which usually means you have installed it manually - i.e. not with the package management system.
I assume you are familiar with Windows, so I'd like a draw an analogy. Lets say you get an application which is in a .zip file - there is no installer - the zip file just contains containing a .exe file and a few .dlls and data files. You unzip this in C:\myapp\. In this case you would no expect to be able to go to add/remove programs to un-install it - it has not been registered with the OS - you must manually delete it.
The same thing goes for any software which you install on a debian/ubuntu system where you do not use one of th front ends to the package management system (apt-get or aptitude or adept or synaptic and so on).
When you build software from source, it does not use the package management system. Some (but not all) projects provide a "make uninstall" target. If you have this, and remember building and installing with "make install", you should be fine to use it.
If there is no "make uninstall" target, you simply have to go and delete the files for th program. This can be a little fiddly because the file system layout means the files are split over several areas - the binary goes in <prefix>/bin, the libraries go in <prefix>/lib, and so on.
For this reason, when I am building from source, I usually set the <prefix> to be /opt/<applicationname>/
This way, everything gets installed under one directory, and if I want to get rid of it, I just delete that directory. The down-side is that the binary will not be in the PATH, and if there are libraries to load, I sometimes need to set the LD_LIBRARY_PATH. For me this is worth the effort for the clean un-install.
Thank you for your response. The 'make uninstall' did the job. Next time I'll have the balls to delete if it's necessary.
Thank you for your response. The 'make uninstall' did the job. Next time I'll have the balls to delete if it's necessary.
hehe, no worries. The rule of thumb is - is you can install with the package manager, do that. In the case of wine, they do a build of every release and package it for ubuntu/debian. You can add their repository and then just update and install wine, and you will have th latest version.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.